Domain-Driven Development
Public.icon
In the past, I thought the value of creating business systems was in efficiency and speed. Now, I think those are rather secondary effects. The main focus of systems engineering should be to create a new harmony of the stairs among the people involved in the business. And to do that, it is necessary to understand the various forces at work in the domain. In accounting, there are complex financial reports. The field departments are overwhelmed by monthly budget variances. The management is anxious because they cannot see the end of the period. They do not understand the situation of the subsidiary. Where should we go next from such stairs? What kind of harmony can we find among these various forces? That is the challenge of systems engineering.
No matter where the new "stairs" are, IT is necessary to reach them. System engineers are influencing the future of the domain more than they think. Nevertheless, most engineers do not commit to the future of the domain and think it is someone else's problem. It is regrettable for both the domain and the engineers.
Recently, there was a discussion about the "Museum Archive" issue from the engineer's side. It was very interesting and informative. If such discussions arise in every domain that engineers are involved in, both Domain and Systems Engineering will become more creative and exciting worlds.